home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Base Documentation 1998 November
/
IRIX 6.5.2 Base Documentation November 1998.img
/
usr
/
share
/
catman
/
u_man
/
cat1
/
routeprint.z
/
routeprint
Wrap
Text File
|
1998-10-30
|
11KB
|
265 lines
RRRROOOOUUUUTTTTEEEEPPPPRRRRIIIINNNNTTTT((((1111)))) PPPPrrrriiiinnnnttttiiiinnnngggg TTTToooooooollllssss RRRROOOOUUUUTTTTEEEEPPPPRRRRIIIINNNNTTTT((((1111))))
NNNNAAAAMMMMEEEE
routeprint, fileconvert - convert file to printer or to specified
filetype
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
rrrroooouuuutttteeeepppprrrriiiinnnntttt [----cccc filetypeDatabasePath ] [----gggg] [ [----pppp printer] | [----dddd
destination-type] ] [----tttt source-type] files
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
_r_o_u_t_e_p_r_i_n_t is a utility accessible from the IRIX command line to request
a Bourne Shell command line which will convert the given file to the
requested format. _r_o_u_t_e_p_r_i_n_t may also be used to convert files of
various types to print on one of a set of desired printers. _r_o_u_t_e_p_r_i_n_t
uses file types specified on the command line to look up print conversion
rules for each file to be printed. The conversion rules are located in
compiled ._o_t_r files in /_u_s_r/_l_i_b/_f_i_l_e_t_y_p_e. The older _f_t_r(_1) database
format, ._c_t_r files are not supported anymore. The source ._f_t_r files can
be found in the _l_o_c_a_l, _i_n_s_t_a_l_l, _s_y_s_t_e_m, and _d_e_f_a_u_l_t subdirectories under
/_u_s_r/_l_i_b/_f_i_l_e_t_y_p_e. If no file types are specified on the command line,
_r_o_u_t_e_p_r_i_n_t looks up the appropriate type for each file. _r_o_u_t_e_p_r_i_n_t uses
the print conversion rules to process the files into the form requested
or a form printable by the target printer.
_p_r_i_n_t_e_r is the name of a printer to which the output may be sent.
_d_e_s_t_i_n_a_t_i_o_n-_t_y_p_e is the name of a destination filetype to which the
output should be converted.
_s_o_u_r_c_e-_t_y_p_e is a file-type name.
_f_i_l_e_s is one or more file names, separated by spaces.
----gggg The ----gggg option should be used when _r_o_u_t_e_p_r_i_n_t is defined as part
of a file typing rule. This option puts error messages in a
notifier window (instead of sending them to stdout) and
suppresses warnings.
----cccc _f_i_l_e_t_y_p_e_D_a_t_a_b_a_s_e_P_a_t_h The ----cccc option allows users to specify an
alternate file typing rules database, ._o_t_r file to use. This
option should be used to override the default FTR database search
path, which is /usr/lib/filetype/desktop.otr. In older versions,
_r_o_u_t_e_p_r_i_n_t used to also search in the user's HOME directory,
before looking under, /usr/lib/filetype directory. This is not
supported anymore, but the users can still give their own FTR
database using the ----cccc flag. Also, note that the old FTR database
file format, ._c_t_r, is not supported anymore, it is replaced by
the new ._o_t_r file format. By default, if an invalid database is
given, _r_o_u_t_e_p_r_i_n_t automatically rejects that database, and loads
the default _d_e_s_k_t_o_p._o_t_r database.
PPPPaaaaggggeeee 1111
RRRROOOOUUUUTTTTEEEEPPPPRRRRIIIINNNNTTTT((((1111)))) PPPPrrrriiiinnnnttttiiiinnnngggg TTTToooooooollllssss RRRROOOOUUUUTTTTEEEEPPPPRRRRIIIINNNNTTTT((((1111))))
----dddd _d_e_s_t_i_n_a_t_i_o_n-_t_y_p_e is specified as the target filetype for the
conversion. _R_o_u_t_e_p_r_i_n_t will determine whether a conversion path
exists between the input file's type and the specified
_d_e_s_t_i_n_a_t_i_o_n-_t_y_p_e. If no conversion path exists, _r_o_u_t_e_p_r_i_n_t will
return an exit code other than 0 and an empty string. If a
conversion path exists, _r_o_u_t_e_p_r_i_n_t will return an exit code of 0
and a string representing the commands necessary to execute in
order to convert the file from the source type to the destination
type. This string may in turn be executed as a Bourne Shell
program or as the argument to _s_y_s_t_e_m to produce the destination
filetype on _s_t_d_o_u_t.
The ----pppp and ----dddd options are mutually exclusive, and the ----dddd option may
appear only once on the command line. The ----pppp or ----tttt options may appear
multiple times on the command line, and are used in the following way:
----pppp _p_r_i_n_t_e_r is added to the collection of printers on which the
output may appear. Each instance of the ----pppp option on the command
line adds one printer to this collection. If more than one
printer is specified, _r_o_u_t_e_p_r_i_n_t uses the print conversion rules
to determine the best printer to use. If no printer names are
given via the ----pppp flag, the destination printer is the system
default printer. Using the ----pppp option overrules the system
default printer.
----tttt _s_o_u_r_c_e-_t_y_p_e sets the filetype for the files that follow it on the
command line until another type is specified. If no type is
given via the ----tttt flag, or files appear on the command line before
the first ----tttt, the files are typed by _r_o_u_t_e_p_r_i_n_t. _r_o_u_t_e_p_r_i_n_t
examines all of the specified files' types. If they are
identical, a single print job will be initiated. If the types
are varied, _r_o_u_t_e_p_r_i_n_t generates an error message.
The system default printer is the printer or printer class on which a
print job appears if no printer is specified with the ----pppp option. The
system default printer is normally specified using the _P_r_i_n_t_e_r _M_a_n_a_g_e_r in
the _S_y_s_t_e_m menu on the _t_o_o_l_c_h_e_s_t(_1).
UUUUSSSSAAAAGGGGEEEE
A typical call from the command line might look like the following:
routeprint -p myprinter file1 file2 file3
A typical call requesting a file conversion command line might look like
the following:
routeprint -d PostScriptFile file1
PPPPaaaaggggeeee 2222
RRRROOOOUUUUTTTTEEEEPPPPRRRRIIIINNNNTTTT((((1111)))) PPPPrrrriiiinnnnttttiiiinnnngggg TTTToooooooollllssss RRRROOOOUUUUTTTTEEEEPPPPRRRRIIIINNNNTTTT((((1111))))
JJJJOOOOBBBB OOOORRRRDDDDEEEERRRRIIIINNNNGGGG
The ordering of files specified on _r_o_u_t_e_p_r_i_n_t's command line determines
the ordering of files within the resultant print job.
PPPPRRRRIIIINNNNTTTT CCCCOOOONNNNVVVVEEEERRRRSSSSIIIIOOOONNNN RRRRUUUULLLLEEEESSSS
The ._f_t_r file used by _r_o_u_t_e_p_r_i_n_t contains both file type rules and print
conversion rules.
The following is a typical set of print conversion rules:
CONVERT TroffFile PostScriptFile
COST 50
FILTER psroff -t $file
CONVERT PostScriptFile myLaserPrinterType
COST 50
FILTER lp -d $CURRENTPRINTER
The CONVERT item specifies the file type of the input file followed by
the file type of the converted file.
The COST item specifies an arbitrary number between 0 and 1000
(inclusive) that represents the image degradation and processing cost
inherent in the conversion. The higher the COST value, the more
_r_o_u_t_e_p_r_i_n_t will try to avoid printing by that specific conversion method,
if it is given a choice.
The conventions for determining what COST to assign a given conversion
are as follows:
COST REASON
0 Equivalent filetypes, or a SETVAR rule.
50 Default conversion cost.
125 Trivial data loss, or conversion is expensive.
200 Minor data loss AND conversion is not expensive.
300 Noticeable data loss AND conversion is expensive.
500 Obvious data loss. (E.g., Color to Monochrome.)
The FILTER item contains the shell command that performs the conversion.
Given the conversion rules above, the command:
routeprint -p myLaserPrinterType -t TroffFile myfile.troff
would cause the file mytroff.t to be printed on the printer named
``mylaserprinter'' via the _p_s_r_o_f_f and _l_p commands. Note that more than
one conversion rule may be used to actually get the files into a
printable form.
PPPPaaaaggggeeee 3333
RRRROOOOUUUUTTTTEEEEPPPPRRRRIIIINNNNTTTT((((1111)))) PPPPrrrriiiinnnnttttiiiinnnngggg TTTToooooooollllssss RRRROOOOUUUUTTTTEEEEPPPPRRRRIIIINNNNTTTT((((1111))))
FFFFIIIILLLLEEEESSSS
/usr/lib/filetype/local/*.ftr
/usr/lib/filetype/install/*.ftr
/usr/lib/filetype/system/*.ftr
/usr/lib/filetype/default/*.ftr
/usr/lib/filetype/desktop.otr
KKKKNNNNOOOOWWWWNNNN BBBBUUUUGGGGSSSS
The maximum length of strings returned are currently harcoded. The
command string returned by _r_o_u_t_e_p_r_i_n_t cannot exceed 4096 characters,
including terminating NULL, or routeprint's behavior will be undefined.
_r_o_u_t_e_p_r_i_n_t does not currently support the use of multiple filetypes.
SSSSEEEEEEEE AAAALLLLSSSSOOOO
_I_R_I_X _I_n_t_e_r_a_c_t_i_v_e _D_e_s_k_t_o_p _I_n_t_e_g_r_a_t_i_o_n _G_u_i_d_e , _r_o_u_t_e_p_r_i_n_t(_1), _f_t_r(_1), _s_h(_1)
PPPPaaaaggggeeee 4444